Dynamic gap control for automated driving

ABSTRACT

A variety of methods, controllers and algorithms are described for controlling a vehicle to closely follow one another safely using automatic or partially automatic control. The described control schemes are well suited for use in vehicle platooning and/or vehicle convoying applications, including truck platooning and convoying controllers. In one aspect, a power plant (such as an engine) is controlled using a control scheme arranged to attain and maintain a first target gap between the vehicles. Brakes (such as wheel brakes) are controlled in a manner configured to attain and maintain a second (shorter) target gap. Such control allows a certain degree of encroachment on the targeted gap (sometimes referred to as a gap tolerance) before the brakes are actuated. The described approaches facilitate a safe and comfortable rider experience and reduce the likelihood of the brakes being actuated unnecessarily.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No. 15/605,456, filed on May 25, 2017, which claims priority of U.S. Provisional Patent Application Nos. 62/489,662 filed on Apr. 25, 2017 and 62/377,970, filed on Aug. 22, 2016, all of which are incorporated herein by reference in their entirety.

BACKGROUND

The present invention relates generally to systems and methods for enabling vehicles to closely follow one another safely using automatic or partially automatic control. More particularly, the invention relates to systems and methods for maintaining a desired gap between vehicles.

In recent years significant strides have been made in the field of automated vehicle control. One segment of vehicle automation relates to vehicular convoying systems that enable vehicles to follow closely together in a safe, efficient and convenient manner Following closely behind another vehicle has the potential for significant fuel savings benefits, but is generally unsafe when done manually by the driver. One type of vehicle convoying system is sometimes referred to as vehicle platooning in which a second, and potentially additional, vehicle(s) is/are automatically or semi-automatically controlled to closely follow a lead vehicle in a safe manner.

The fuel efficiency advantages of platooning are particularly noticeable in fields such as the trucking industry in which long distances tend to be traveled at highway speeds. One of the on-going challenges of vehicle platooning and convoying systems is controlling the gap between the platooning vehicles. The potential fuel economy gains generally improve the closer the platooning vehicle travel together. At the same time, the reaction time potentially available for responding to changes initiated by the lead vehicle is shortened as the gap shortens which can make the gap control more challenging. At times, braking may be required to prevent a trailing vehicle from getting too close to a leading vehicle. Frequent braking and/or the frequent use of other fuel inefficient gap control techniques can quickly erode the potential fuel efficiency advantages of platooning and convoying systems.

Although existing gap control techniques work well, there are continuing efforts to develop improved gap control methods and systems that provide safe and fuel efficient operation as well as a comfortable user experience. The present application describes techniques for controlling the gap between vehicles that are well suited for platooning, convoying and other automated or semi-automated driving applications.

SUMMARY

A variety of methods, controllers and algorithms are described for controlling a vehicle to closely follow one another safely using automatic or partially automatic control. The described control schemes are well suited for use in vehicle platooning and/or vehicle convoying applications, including truck platooning and convoying controllers.

In one aspect, a power plant (such as an engine) is controlled using a control scheme arranged to attain and maintain a first target gap between the vehicles. Brakes (such as wheel brakes) are controlled in a manner configured to attain and maintain a second (shorter) target gap. Such control allows a certain degree of encroachment on the targeted gap (sometimes referred to as a gap tolerance) before the brakes are actuated. The described approaches facilitate a safe and comfortable rider experience and reduces the likelihood of the brakes being actuated unnecessarily—which can improve fuel economy. It also has the potential to reduce braking system maintenance costs—particularly in the context of platooning or convoying trucks where the unnecessary use of foundation brakes can lead to more frequent costly brake repairs/replacement.

In some embodiments, if it is determined that the lead vehicle is braking (or is imminently going to brake), the brake control is switched to a control scheme that has the same gap target as the engine control in some circumstances and/or to a control scheme that has an intermediately target between the first and second target gaps—as for example a target configured to maintain the current gap encroachment when a portion of the gap tolerance is already encroached when the front vehicle braking is identified.

In some embodiments a platoon controller that includes separate engine output (e.g. torque) request and braking request controllers is provided to implement the described control. In such an arrangement the torque and braking request controllers can readily be configured to control towards different gap targets. The respective gap targets can be independent adjusted on the fly to provide the control characteristics appropriate for the current operating conditions.

In some embodiments, the engine output and braking request controllers take the form of sliding mode controllers.

In applications where the host vehicle includes a retarder (as will often be the case in heavy truck control applications), retardation and/or other types of engine braking may be invoked as part of the engine torque control, with the wheel brakes being responsive to the brake request controller but not the torque request controller.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention and the advantages thereof, may best be understood by reference to the following description taken in conjunction with the accompanying drawings in which:

FIG. 1 is a block diagram of a controller architecture suitable for use in an automated or partially automated vehicle control system that supports platooning.

FIG. 2 is a block diagram of a representative platoon controller architecture suitable for use in the automated or partially automated vehicle control system of FIG. 1.

FIG. 3 is a block diagram of a gap controller in accordance with one embodiment.

FIGS. 4A-4C are a series of diagrams illustrating different control states used by a gap regulator in accordance with one embodiment during different operational states.

FIG. 5A is a state space diagram illustrating a control scheme in which torque requests and braking request are controlled towards different gaps in accordance with an embodiment of the invention.

FIG. 5B is a reproduction of the state space diagram of FIG. 5A with the state transition lines removed for clarity.

FIG. 6 is a state space diagram similar to FIG. 5B illustrating a scenario in which the braking request control is adjusted to coincide with the torque request control in a portion of the control space.

FIG. 7 is a state space diagram similar to FIG. 5B illustrating a gap usage adjusted braking request control scheme.

In the drawings, like reference numerals are sometimes used to designate like structural elements. It should also be appreciated that the depictions in the figures are diagrammatic and not to scale.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention will now be described in detail with reference to several embodiments thereof as illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention, including the description of a plurality of different aspects of the invention, including, in some case, one or more alternatives. It will be apparent to those skilled in the art that the invention can be practice without implementing all of the features disclosed herein.

The Applicant has proposed various vehicle platooning systems in which a second, and potentially additional, vehicle(s) is/are automatically, or semi-automatically controlled to closely follow a lead vehicle in a safe manner By way of example, U.S. application Ser. Nos. 13/542,622 and 13/542,627; U.S. Provisional Application Nos. 62/377,970 and 62/343,819; and PCT Application Nos. PCT/US2014/030770, PCT/US2016/049143 and PCT/US2016/060167 describe various vehicle platooning systems in which a trailing vehicle is at least partially automatically controlled to closely follow a designated lead vehicle. Each of these earlier applications is incorporated herein by reference.

One of the goals of platooning is typically to maintain a desired longitudinal distance between the platooning vehicles, which is frequently referred to herein as the “desired gap”. That is, it is desirable for the trailing vehicle (e.g., a trailing truck) to maintain a designated gap relative to a specific vehicle (e.g., a lead truck). The vehicles involved in a platoon will typically have sophisticated control systems suitable for initiating a platoon, maintaining the gap under a wide variety of different driving conditions, and gracefully dissolving the platoon as appropriate.

The architecture and design of control systems suitable for implementing vehicle platooning may vary widely. The specific controller design can vary based on the level of automation contemplated as part of the platoon, as well as the nature of and equipment available on the host vehicles participating in the platoon. By way of example, FIG. 1 diagrammatically illustrates a vehicle control architecture that is suitable for use with platooning tractor-trailer trucks. The specific controller illustrated is primarily designed for use in conjunction with a platooning system in which both vehicles include an active driver. The driver of the lead vehicle being fully responsible for control of the front vehicle. The a driver of the trailing vehicle is responsible for steering the trailing vehicle, but the platoon controller 110 is primarily responsible for controlling the trailing vehicle's torque and braking requests during active platooning. However it should be appreciated that generally similar control schemes can be used in systems which contemplate more automated control of one or both of the platoon partners.

In the illustrated embodiment illustrated in FIG. 1, a platoon controller 110, receives inputs from a number of sensors 130 on the tractor and/or one or more trailers or other connected units, and a number of actuators and actuator controllers 150 arranged to control operation of the tractor's powertrain and other vehicle systems. An actuator interface 160 may be provided to facilitate communications between the platoon controller 110 and the actuator controllers 150. The platoon controller 110 also interacts with an inter-vehicle communications controller 170 which orchestrates communications with the platoon partner and a NOC communications controller 180 that orchestrates communications with a network operations center (NOC). The vehicle also preferably has selected configuration files 190 that include known information about the vehicle.

Some of the functional components of the platoon controller 110 include gap controller 112, a variety of estimators 114, one or more partner vehicle trackers 116 and various monitors 118. In many applications, the platoon controller 110 will include a variety of other components 119 as well. Exemplary embodiments of the platoon controller 110 and gap controller 112 are described in more detail below with reference to FIGS. 2 and 3.

Some of the sensors utilized by the platoon controller 110 may include GNSS (GPS) unit 131, wheel speed sensors 132, inertial measurement devices 134, radar unit 137, LIDAR unit 138, cameras 139, accelerator pedal position sensor 141, steering wheel position sensor 142, brake pedal position sensor 143, and various accelerometer 144. Of course, not all of these sensors will be available on all vehicles involved in a platoon and not all of these sensors are required in any particular embodiment. A variety of other sensor 149 (now existing or later developed or commercially deployed) may be additionally or alternatively be utilized by the platoon controller in other embodiments. In the primary embodiments described herein, GPS position data is used. However, GPS is just one of the currently available global navigation satellite systems (GNSS). Therefore, it should be appreciated that data from any other GNSS system or from other suitable position sensing systems may be used in place of, or in addition to the GPS system.

Many (but not all) of the described sensors, including wheel speed sensors, 132, radar unit 137, accelerator pedal position sensor 141, steering wheel position sensor 142, brake pedal position sensor 143, and accelerometer 144 are relatively standard equipment on newer trucks (tractors) used to pull semi-trailers. However, others, such as the GNSS unit 131 and LIDAR unit 138 (if used) are not currently standard equipment on such tractors or may not be present on a particular vehicle and may be installed as needed or desired to help support platooning.

Some of the vehicle actuators controllers 150 that the platoon controller may direct at least in part include engine torque controller 152 (which is often part of the integrated functionality of an engine control unit (ECU) or power train control module (PCM)); transmission controller 154; brake controller 156; steering controller 157 (when automated steering is provided); and clutch controller 158. Of course, not all of these actuator controllers will be available or are required in any particular embodiment and it may be desirable to interface with a variety of other vehicle actuator controllers 159 that may be available on the controlled vehicle as well. Therefore, it should be appreciated that the specific actuator controllers 150 directed or otherwise utilized by the platoon controller on any particular controlled vehicle may vary widely. Further, the capabilities of any particular actuator controller (e.g. engine torque controller 152), as well as its interface (e.g., the nature and format of the commands, instructions, requests and messages it can handle or generate) will often vary with the make and model of that particular actuator controller. Therefore, an actuator interface 160 is preferably provided to translate requests, commands, messages and instructions from the platoon controller 110 into formats that are appropriate for the specific actuator controller hardware and software utilized on the controlled vehicle. The actuator interface 160 also provides a mechanism for communicating/translating messages, commands, instructions and requests received from the various actuator controllers back to the platoon controller 110. Typically an appropriate actuator interface would be provided to interact with each of the specific vehicle controllers utilized. In various embodiments, this may include one or more of: an engine torque interface 161; a brake interface 162; a transmission interface 164; a retarder interface 165 (if a separate retarder controller is used); a steering interface 167; and/or any other appropriate controller interface 169.

Large trucks and other heavy vehicles frequently have multiple systems for “braking” the truck. These include the traditional brake system assemblies mounted in the wheels of the vehicle—which are often referred to in the industry as the “foundation brakes.” Most large trucks/heavy vehicles also have a mechanism referred to as a “retarder” that is used to augment the foundation brakes and serve as an alternative mechanism for slowing the vehicle or to help prevent the vehicle from accelerating down a hill. Often, the retarder will be controlled by the engine torque controller 152 and in such embodiments, the retarder can be controlled by sending appropriate torque commands (which may be negative) to the engine torque controller 152. In other embodiments a separate retarder controller (not shown) may be accessible to, and therefore directed by, platoon controller 110 through an appropriate retarder interface 165.

The communications between vehicles may be directed over any suitable channel and may be coordinated by inter-vehicle communications controller 170. By way of example, the Dedicated Short Range Communications (DSRC) protocol, which is a two-way short to medium range wireless communications technology that has been developed for vehicle to vehicle communications, works well. The specific information transmitted back and forth between the vehicles may vary widely based on the needs of the platoon controller.

The communications between vehicles may be directed over any suitable channel and may be coordinated by inter-vehicle communications controller 170. By way of example, the Dedicated Short Range Communications (DSRC) protocol (e.g. the IEEE 802.11p protocol), which is a two-way short to medium range wireless communications technology that has been developed for vehicle to vehicle communications, works well. Of course other communications protocols and channels may be used in addition to or in place of a DSRC link. For example, the inter vehicle communications may additionally or alternatively be transmitted over a Citizen's Band (CB) Radio channel, one or more General Mobile Radio Service (GMRS) bands, and one or more Family Radio Service (FRS) bands or any other now existing or later developed communications channels using any suitable communication protocol.

In various embodiments, the transmitted information may include the current commands generated by the platoon controller 110 such as requested/commanded engine torque 280, requested/commanded braking deceleration 282. They may also include steering commands, gear commands, etc. when those aspects are controlled by platoon controller 110. Corresponding information is received from the partner vehicle, regardless of whether those commands are generated by a platoon controller or other suitable controller on the partner vehicle (e.g., an adaptive cruise control system (ACC) or a collision mitigation system (CMS)), or through other or more traditional mechanisms—as for example, in response to driver inputs (e.g., accelerator pedal position, brake position, steering wheel position, etc.).

In many embodiments, much or all of the tractor sensor information provided to platoon controller 110 is also transmitted to the platoon partner and corresponding information is received from the platoon partner so that the platoon controllers 110 on each vehicle can develop an accurate model of what the partner vehicle is doing. The same is true for any other relevant information that is provided to the platoon controller, including any vehicle configuration information 190 that is relevant to the platoon controller. It should be appreciated that the specific information transmitted may vary widely based on the requirements of the platoon controllers 110, the sensors and actuators available on the respective vehicles, and the specific knowledge that each vehicle may have about itself.

The information transmitted between vehicles may also include information about intended future actions. For example, if the lead vehicle knows it approaching a hill, it may expect to increase its torque request (or decrease its torque request in the context of a downhill) in the near future and that information can be conveyed to a trailing vehicle for use as appropriate by the platoon controller 110. Of course, there is a wide variety of other information that can be used to foresee future torque or braking requests and that information can be conveyed in a variety of different forms. In some embodiments, the nature of the expected events themselves can be indicated (e.g., a hill, or curve or exit is approaching) together with the expected timing of such events. In other embodiments, the intended future actions can be reported in the context of expected control commands such as the expected torques and/or other control parameters and the timing at which such changes are expected. Of course, there are a wide variety of different types of expected events that may be relevant to the platoon control.

The communications between the vehicles and the NOC may be transmitted over a variety of different networks, such as the cellular network, various Wi-Fi networks, satellite communications networks and/or any of a variety of other networks as appropriate. The communications with the NOC may be coordinated by NOC communications controller 180. The information transmitted to and/or received from the NOC may vary widely based on the overall system design. In some circumstances, the NOC may provide specific control parameters such as a target gap tolerance. These control parameters or constraints may be based on factors known at the NOC such as speed limits, the nature of the road/terrain (e.g., hilly vs. flat, winding vs. straight, etc.) weather conditions, traffic or road conditions, etc. In other circumstances the NOC may provide information such information to the platoon controller. The NOC may also provide information about the partner vehicle including its configuration information and any known relevant information about its current operational state such as weight, trailer length, etc.

The configuration file 190 may include a wide variety of information about the host vehicle that may be considered relevant to the controller. By way of example, some of the information might include the vehicle's specification including such things as engine performance characteristics, available sensors, the nature of its braking system, the location of its GNSS antenna relative to the front of the cab, gear ratios, differential ratios etc.

FIG. 2 illustrated a particular embodiment of a platoon controller 110. In the illustrated embodiment, the platoon controller 110 includes a gap controller 112, a plurality of estimators 114, one or more trackers 116, any desired monitors 118 and potentially any of a variety of other components 119.

In the illustrated embodiment, the gap controller 112 includes a target and state setter 200, a gap regulator 210 and a gap estimator 240. In general, the target and state setter 200 is arranged to determine the intended operational mode (state) of the gap regulator 210 and the values of any variable control parameters that are appropriate for use in that operational mode.

The gap regulator 210 is arranged to control the trailing platoon partner in the manner designated by the target and state setter 200. In the gap control operational mode, the gap regulator 210 controls the vehicle in a manner that seeks to attain and maintain the desired gap in accordance with any designated control parameters specified by the state setter 200. In other modes, the gap regulator 210 controls the vehicle in a manner that seeks to attain the appropriate response for the selected operational mode.

The gap estimator 240 is arranged to estimate/determine the current gap based on actual measurements and/or other information that is available to the platoon controller 110. It should be apparent that an accurate understanding of the current gap is important to successful operation of the gap regulator. At the same time, it should be appreciated that any measurement system has inherent tolerances and can be subject to reporting errors and/or may become unavailable in some circumstances. Thus, the gap estimator 240 is configured to receive information from multiple position or relative position related sensors and to fuse such data into a reliable estimate of the current gap.

The torque and braking requests generated by GAP regulator 210 are sent to the appropriate actuator interface (e.g., engine torque interface 161 and brake interface 162 respectively). The engine torque interface 161 then forwards an appropriate torque command to engine torque controller 152 which directs the delivery of the requested torque by directing various engine operating parameters such as fuel charge, valve timing, retarder state, etc. appropriately. The brake interface 162 generates an appropriate brake request that is sent to the brake controller 156.

A particular embodiment of gap controller 112 is described in more detail below with reference to FIG. 3.

Returning to FIG. 2, there are a variety of estimators 114 that are useful for the gap controller 112. In various embodiments these may include one or more of a mass estimator 271, a drag estimator 273, a ground speed estimator 275, a gyro bias estimator 277 and/or other estimators 279.

The mass estimator 271 is arranged to estimate the respective masses of the platoon partners. These mass estimations may be used by the gap controller 112 to help scale its torque and brake requests appropriately based on the respective weights (masses) of the platoon partners.

The drag estimator 273 is arranged to estimate the respective drag resistances of the platoon partners. These drag resistance estimates may also be used by the gap controller to help adjust its torque and brake requests appropriately. In general, the drag resistance of any particular truck or other vehicle can vary based on a variety of factors including: (a) its drag profile (which in the context of a truck may change based on the trailer being pulled—if any, or other characteristics of the load); (b) the vehicle's current speed, (c) wind speed and direction, (d) rolling resistance, (e) platoon state (e.g., whether a platoon is active, the position of the vehicle within the platoon, the gap), (f) bearing wear, etc.

The ground speed estimator 275 is arranged to estimate the actual ground speed of the respective platoon partners. Many trucks and other vehicles have wheel speed sensors that can quite accurately measure the rotational speed of the associated wheels. The actual ground speed at which the vehicles are traveling will vary based on the respective diameters of the wheels and slip conditions of the tires. The precise diameter of the wheels can vary based on the tires used. Furthermore, the diameter of the wheels will vary over time with tire wear, changes in ambient temperature and other factors. The wheel diameter will even change over the course of a particular trip as the tires heat up (or otherwise change in temperature) during use. In practice, all of these variations in wheel diameter are potentially significant enough to impact the gap estimation and gap control. Therefore, the ground speed estimator 275 is arranged to estimate the actual ground speed based on measured wheel speed and other available information such as GNSS information. The ground speed estimates are particularly useful in times when tracker based gap measurements (e.g., radar, cameras, LIDAR, etc.) aren't available—which may occur, for example, when the platoon partners are laterally offset due to a lane change, etc.

Several of the measurements utilized by the gap controller 112 are inertial measurements that are gyro based. These may include yaw measurements which indicate the rate at which the associated vehicle is turning, longitudinal acceleration measurements, etc. Gyros often have an inherent measurement error referred to as a gyro bias that can affect measurements. The gyro bias estimator 277 estimates such biases to allow the gap controller to compensate for such gyro based measurement errors.

The platoon controller 110 can include any other estimators 279 that may be useful to any particular gap controller 112 as well.

The platoon controller 110 may also include one or more trackers 116. Each tracker 116 is arranged to measure or otherwise determine the gap. One type of tracker that is used in many implementations is a radar based tracker 283. Newer commercially available trucks often come equipped with a radar unit as standard equipment and radar trackers are particularly well suited for use in such vehicles. Of course, one or more radar units may be installed on any vehicle that does not come pre-equipped with a radar unit to facilitate use of radar tracker 283. By way of example, some specific radar trackers are described in more detail in co-pending U.S. application Ser. Nos. 15/590,715 and 15/590,803, both filed May 9, 2017, both of which are incorporated herein by reference.

LIDAR is another distance measuring technology that is well suited for measuring the gap between vehicles. LIDAR is quickly gaining popularity for use in automated and autonomous driving applications. LIDAR tracker 286 is well suited for use on vehicles that have or are provided with LIDAR units. Cameras and stereo cameras are also becoming more popular distance measuring tools for use in various automated and autonomous driving applications.

Of course, other distance measuring technologies can be used to measure or estimate the gap between vehicles as represented by other trackers 289. By way of example, a GPS tracker could be used that is based primarily on the respective reported GPS positions of the vehicles.

The tracker(s) used in many embodiments are configured to fuse data from multiple sensors to help validate the measurements of the primary sensors used by the respective trackers. The aforementioned radar tracker application describes a variety of methods for fusing data to help validate measurements of a primary sensor in that manner.

In various embodiments, the gap estimator 240 could replace or be replaced by one or more of the trackers, or could be thought of as a tracker itself since it determines/estimates the gap based on inputs from multiple sensors. In the illustrated embodiment, the gap estimator 240 is shown separately as part of gap controller 112 since it fuses distance data from the tracker(s) and any other available sources such as GNSS sensors on each of the vehicles.

The platoon controller 110 may also include one or more monitors 118 that are configured to monitor specific components that are relevant to gap control. By way of example, one specific monitor that is particularly useful to the control of platooning trucks is brake health monitor 291. The brake health monitor 291 is configured to monitor the brake system and to identify circumstances in which the brakes may not be able to deliver the level of braking normally expected for platoon control—as for example could occur if the foundation brakes include drum brakes that have been used while traveling downhill in the mountains to the extent that they are close to overheating. If the brake health monitor 291 identifies such a circumstance, it informs the platoon controller, which can take the appropriate remedial action. The appropriate remedial action will vary based on the specific circumstances identified by the brake health monitor, but may include, for example, actions such as dissolving the platoon, increasing the target gap to a level more appropriate for the brake conditions, etc. Of course, the brake health monitor can also configured to identify circumstances in which the condition of the brakes has improved (e.g., the brakes have cooled sufficiently) and inform the platoon controller of those circumstances as well so that the platoon controller can act accordingly. For example, improved braking status may allow the target gap to be reduced, a platoon to be reestablished or other appropriate actions.

The platoon controller may include any of a variety of other monitors 299 that are configured to monitor the state or status of other components, systems, environmental conditions, road or traffic conditions, etc. that may be relevant to platoon control. For example, a DSRC link monitor may be provided to monitor the status of a DSRC communication link between the platoon partners.

Referring next to FIG. 3, another embodiment of gap controller 112 will be described in more detail. Similarly to the embodiment illustrated in FIG. 2, the gap controller 112 includes a target and state setter 200, a gap regulator 210 and a gap estimator 240. In the embodiment of FIG. 3, the target and state setter 200 includes an operating state selector 203, and a control parameter selector 206 that determines, selects, sets or otherwise indicates to the gap regulator the values of any variable control parameters that are appropriate for use in the selected operational mode.

The operating state selector 203 is arranged to determine the intended operational mode (state) of the gap regulator 210. In some specific embodiments, the operational modes might include a “normal” or “gap control” operational mode in which the gap regulator is configured to control towards attaining and maintaining a designated gap between the vehicles. In the gap control operational mode control parameter variables dictated by the control parameter selector might include the target gap itself (e.g. 10 m, 12 m, etc.)—which may vary somewhat based on driving conditions (e.g., weather, terrain, road conditions, traffic, etc.). Other control parameters during normal operation may include parameters that impact the draw-in speed, the tightness of the control, tolerances or variations between torque control and braking control, etc. In other embodiments, “initiate platoon” and/or “draw-in” or “pull-in” may be one or more separate states that are used to establish a platoon and/or to bring the platoon partners together in a safe manner under at least partially automated control.

Another potential operational mode is a “dissolve” mode in which the platoon controller transitions the trailing vehicle toward/to a position at which the driver of the trailing vehicle (or an automatic cruise control system) can safely take over control of the vehicle. Generally, dissolving a platoon includes increasing the gap between the vehicles in a controlled manner to/towards a point at which the platoon can be dissolved and vehicle control can be safely transferred to manual control by the driver or to control through the use of a different system such as adaptive cruise control. The dissolve mode may optionally be triggered by a wide variety of different circumstances, as for example, in response to one of the platoon partners or the NOC deciding to terminate the platoon; the detection of a car cutting-in between the platooning vehicles; the loss of communications between the vehicles for an extended period; the detection of an object in front of the lead vehicle that is too slow or too close to the platoon; etc.

Another potential operational mode may be a velocity control or relative velocity control mode. Velocity control, or relative velocity control may be preferable to trying to control to maintain a particular gap in a variety of specific circumstances—as for example when the trailing vehicle's radar (or other) tracking unit loses sight of the partner vehicle, as can occur when there is a lateral offset between the vehicles due to a lane change or other conditions.

Of course, there can be a variety of other operational modes as well.

The gap regulator 210 is arranged to control the trailing platoon partner in the manner designated by the target and state setter 200. In the embodiment illustrated in FIG. 3, the gap regulator 210 includes a scaler 212 and two separate controllers which are used in different combinations in different operating modes. In the illustrated embodiment, the controllers include a sliding mode controller 215 (which performs gap control) and a velocity/relative velocity controller 218. It should be appreciated that in other embodiments, a single controller, additional and/or different may be provided as appropriate for any particular implementation.

In the illustrated embodiment, the feed forward scaler 212 is configured to scale the torque and brake signals from the front vehicle before adding them to the outputs from the sliding mode and relative velocity controllers 215, 218 to create the torque and brake request to the engine and brake controllers. Such scaling may be based on factors such as the respective weights (masses) of the platoon partners, the respective drags of the vehicles, the severity of a braking event (e.g., in high braking scenarios, the braking command may be increased a bit to provide a margin of safety to account for uncertainties in braking performance and reactions times), etc. In other embodiments, such scaling functions can be integrated into the respective controllers themselves if desired.

The sliding mode controller 215 is configured to control the trailing vehicle in a manner that seeks to attain and maintain the desired gap in accordance with the target gap and any other control parameters specified by the control parameter selector 206. Thus, its primary function is gap control. The velocity controller 218 is configured to control the trailing vehicle in a manner that maintains a designated velocity relative to the lead vehicle, or in some circumstances, simply a designated velocity. In the illustrated embodiment, these two separate controllers are provided so that the gap regulator 210 can provide different types of control, as may be appropriate in different operational circumstances. A few specific examples are described with reference to FIGS. 4A-4C. In the described embodiments, both the controllers 215 and 218 are operated continuously during platooning and the selector/adder 250 is used to select the appropriate signals to output based on the current operating mode. An optional braking monitor 255 is a safety feature that may be utilized to help ensure that the brake commands outputted by selector/adder 250 don't overly aggressively brake the trailing vehicle except in where necessary from a safety/crash prevention standpoint. This is to reduce the risk of traffic behind the trailing platoon partner from being impacted by unexpected aggressive braking of the trailing platoon partner.

Normal gap control is illustrated in FIG. 4A. During normal gap control, the sliding mode controller 215 is used to determine torque and brake requests that are appropriate to attain and maintain the target gap set by control parameter selector 206. When appropriate, the torque and brake requests generated by the sliding mode controller 215 may be scaled appropriately by selector/adder 250 based on inputs from feed forward scaler 212. In this normal gap control mode, the outputs of the relative velocity controller 218 are not used in the control of the trailing vehicle.

In some embodiments, the sliding mode controller 215 includes separate torque request and brake request controllers 221, 223 as illustrated in FIG. 3. The torque request and brake request controllers 221, 223 are configured to control the engine and brakes respectively towards different gap targets which tends to provide a smoother, more comfortable ride and reduce the use of wheel brakes (e.g., the foundation brakes in tractor-trailer rigs) compared to control in which the engine and brakes are controlled to the same target gap. Such a gap control architecture is described in more detail in U.S. Provisional application No. 62/489,662, which is incorporated herein by reference. In some implementations, the torque request and brake request controllers 221, 223 are configured as separate sliding mode controllers.

Although the sliding mode controller 215 works very well to control the gap, there will be operational circumstances in which different types of control may be appropriate. For example, a different type of control may be desirable when it is necessary to dissolve a platoon and return the trailing vehicle to manual or other automated control. Typically, the gap between vehicles during platooning will be smaller, often much smaller, than can safely be maintained by a driver under manual control. Therefore, in general, when a platoon is dissolved with the intent to restoring manual control of the trailing vehicle, it will be desirable to grow the gap to a distance that is appropriate for manual control before relinquishing control to the driver. This can be accomplished in a smooth manner by relative velocity controller 218.

When operating state selector 203 determines that the platoon should be dissolved, it directs the GAP regulator 210 to transition to a dissolve mode as represented by FIG. 4B. In the dissolve mode, primary control is provided by relative velocity controller 218. The control parameter selector 206 may designate a desired (target) relative velocity for the trailing truck during the dissolve. The specific target relative velocity may vary based on the nature of the circumstances and/or the vehicles involved in the platoon. In general, it is desirable to select a relative velocity that will cause the vehicles to gradually, but expeditiously separate, without requiring the trailing vehicle to slow excessively (which could unduly hinder following traffic) and preferably without requiring the lead vehicle to alter its drive plan. By way of example, relative velocities during dissolves on the order of 0.5 to 4 meters per second, as for example, 1-2 m/s, have been found to work well in the context of platooning trucks.

During a dissolve, the lead vehicle may take a variety of actions. For example, the lead truck may accelerate or increase its torque command aggressively. In such cases, it may not be desirable to try to accelerate the trailing truck in a similar manner thereby allowing the lead vehicle to pull away more than would otherwise occur under relative velocity control. One way to accomplish this in the context of platooning trucks is to ignore or otherwise disable positive torque commands from feed forward scaler 212.

Another potential scenario is that the lead truck brakes or slows significantly while under velocity control. In some circumstances, the velocity controller 218 may be configured to permit a certain amount of gap shrinkage when the gap is relatively larger to thereby reduce the overall amount of braking required. In the illustrated embodiment, the sliding mode controller is configured to ensure that the gap between the vehicles is always sufficient to give the trailing vehicle sufficient time to respond in a manner that prevents the trailing vehicle from running into the back of the lead vehicle regardless of the occurrence of (reasonable) unexpected events. Therefore, if the sliding mode controller is outputting a braking or negative torque signal that has a greater magnitude than the relative velocity controller, then that larger braking/negative torque command should be passed to the vehicle's engine and braking controllers. Therefore, during a dissolve, the selector/adder 250 is configured to only utilize negative commands (i.e., braking commands and negative torque commands) from the sliding mode controller 215 and to only use such commands when they are greater in magnitude than the commands from the relative velocity controller 218.

There may also be operational circumstances outside of dissolves in which relative velocity control or simply velocity control is desired. For example, there may be circumstances in which the back of the lead vehicle moves out of view of the trailing vehicle's tracker(s) 116 or the tracker(s) 116 otherwise loses sight of the back of the platoon partner. This can occur, for example, as a result of a lane change by one of the platoon partners. In such a circumstance the gap regulator may not have an accurate measure of the longitudinal gap between the vehicles—and may have to rely on less accurate approaches for determining the gap such as the vehicle's respective GNSS positions. In such circumstances, it may be desirable to control the trailing vehicle to slowly drop back until the back of the lead vehicle comes within the tracker's view. Again, the relative velocity controller 218 is well suited for use in this circumstance—although the preferred relative velocity control may be a bit different than occurs during a dissolve. Specifically, the goal is typically not to drop back as quickly or as far as would occur during a dissolve—thus a smaller relative velocity (e.g. 0.5 m/s vs. 2 m/s), may be appropriate.

One approach to such relative velocity control is illustrated in FIG. 4C. In the velocity control scheme of FIG. 4C velocity controller 218 is used in conjunction with normal scaling from feed forward scaler 212. This causes the trailing platoon partner to better follow lead vehicle accelerations and/or torque increases than occurs during the dissolve state illustrated in FIG. 4B. At the same time, for safety purposes, braking requests and negative torque request from the sliding mode controller 215 may be utilized as appropriate by selector/adder 250 in a manner similar to the approach described above with respect to FIG. 4B.

Although particular platoon and gap controller architectures are illustrated in FIGS. 2 and 3, it should be appreciated that the specific architectures utilized may vary widely to meet the needs of any particular platooning or other automated vehicle control scheme. As will be apparent to those familiar with the art, the described controllers can be implemented algorithmically using software or firmware algorithms executing on one or more processors, using programmable logic, using digital or analog components or using any combination of the preceding.

Gap Regulation

To maintain a desired gap, braking will sometimes be required to slow a trailing vehicle to prevent the trailing vehicle from getting too close to a leading vehicle. Large trucks and other heavy vehicles frequently have multiple systems for “braking” the truck. These include the traditional brake system assemblies mounted in the wheels of the vehicle—which are often referred to in the industry as the “foundation brakes.” Most large trucks/heavy vehicles also have a mechanism referred to as a “retarder” that is used to augment the foundation brakes and serve as an alternative mechanism for slowing the vehicle or to help prevent the vehicle from accelerating down a hill.

A wide variety of different mechanisms can be used as the retarder. The most common type of retarder (often referred to as a “Jake brake”) alters the timing of the engine cylinder exhaust valves to cause compressed air to be released at or near top dead center of its compression stroke which extracts power from the powertrain thereby slowing the vehicle because the engine is effectively working as a compressor. Another type of retarder (often referred to as an exhaust brake) restricts the flow of exhaust gases through the exhaust system, thereby increasing the pressure within the exhaust system, which again forces the engine to work as a compressor in a manner that can help slow the vehicle. Other types of retarders sometimes used include hydraulic retarders and electric retarders. Regardless of the type of retarder used, they all share the same general purpose of serving as an additional or alternative mechanism for braking the vehicle.

Furthermore, even when normal valve timing is used, there will be some pumping losses and some frictional losses in the engine and elsewhere in the powertrain. Therefore, when no fuel is delivered, with the valves operating in the normal manner, the engine and the rest of the powertrain will impart a negative torque—which is referred to herein as a form of “engine braking.” The amount of negative torque imparted by the engine/powertrain (the engine braking) without the use of a retarder can be controlled to some degree by controlling the amount (or lack) of fuel delivered to the cylinders, the transmission gear and sometimes other actuators. However, engine braking without the use of a retarder is inherently limited and therefore there are many driving situations in which it is desirable to provide more affirmative braking through the use of the foundation brakes and/or a retarder.

When affirmative braking is required, it is generally preferable to utilize a retarder rather than the foundation brakes whenever, and to the extent practical. There are several reasons for that general preference. One of the primary reasons for the preference relates to operational costs. Specifically, the foundation brakes wear with usage and wear relatively quickly with heavy usage. Repair and replacement of the brake pads and other foundation brake system components can be expensive and therefore frequent brake repair/replacements increases the overall operational costs. Another reason for the preference is that some retarders, such as Jake brakes, increase the temperature of the exhausts gases relative to the exhaust gas temperatures seen when air is effectively pumped through the cylinders with no fuel being combusted as may occur when the driver releases the accelerator pedal and begins coasting. This helps maintain higher exhaust system temperatures, which is useful for emissions control and tends to help fuel efficiency since it reduces the need to use additional fuel to heat the exhaust system after prolonged periods of braking or coasting. Retarders also tend to provide a smoother braking experience to the driver, which improves ride quality. Therefore, many conventional braking controller for use on heavy trucks are designed with a preference towards using a retarder in favor of the foundation brakes when and to the extent practical. Although retarder use is typically favored, retarders generally cannot slow the vehicle as much as the foundation brakes and their response is more varied and therefore retardation cannot always be used to the exclusion of foundation braking.

With platooning, the desired gap can be maintained the vast majority of the time during normal highway driving by managing the engine torque request alone. That is, more or less torque can be requested as appropriate at any time to maintain the desired gap. The torque request may be sent to the tractor's torque controller 152, which determines the amount of fuel that needs to be injected into each cylinder in order to deliver the requested torque under the current operating conditions (e.g., engine speed, transmission gear, etc.). When more power is needed, the torque request is increased. When less power is needed, the torque request is lowered. In practice, the torque request can even be negative to a degree since some amount of engine braking will inherently occur when no or a very small amount of fuel is injected.

There will, however, be times when more aggressive braking is required as part of platoon control. For example, if the lead truck actively brakes (e.g. when the driver presses the brake pedal) it will typically be desirable to actively brake the trailing vehicle in the same manner. In such circumstance the foundation brakes and/or the retarder are actuated to provide the necessary level of braking. Another example may be when the platoon is cruising downhill. When the grade is relatively steep, the driver of the front truck may release the accelerator pedal. Many powertrain controllers are designed to actively retard when the accelerator pedal is released in at least some operating conditions. One of the rationales for the retarding is to prevent the truck from “running away” (accelerating too much) as it coasts down a hill. When trucks are platooning, the trailing truck will often have to retard or brake more aggressively than the lead truck due to its lower aerodynamic drag.

One possible control scheme contemplates that when affirmative braking (i.e., braking beyond the negative torque provided by the aforementioned fuel cut-off type engine braking) is required, a brake controller is informed of the braking request and the brake controller takes responsibility for determining the amount and apportionment of braking to be applied by the retarder and foundation brakes respectively. Although this approach works well, experiments have shown that in some operational platooning conditions, such an approach tends to lead to use of the foundation brakes more often than might be desired.

One example scenario is when a truck platoon is traveling in a region of rolling hills. When the lead truck passes through a trough and encounters an area with a steeper grade, it may begin to slow down even though its torque request doesn't change or actually increases. At the same time, the following truck is at a shallower grade, flat or possibly still coasting downhill and begins to encroach on the front truck, thereby reducing the gap. The gap controller then takes action to cause the following truck to slow down in an effort to reestablish the desired gap. In some circumstances this may cause actuation of the foundation brakes to slow the trailing truck even though there will imminently be a need to increase torque significantly to prevent the front truck from running away from the trailing truck as the trailing truck subsequently encounters the hill. Such a scenario is undesirable for a number of reasons. Initially, the foundation brakes have been used at a time they probably weren't necessary, which is undesirable from a wear standpoint. Furthermore, passengers in the trailing truck will likely feel the actuation of the foundation brakes at a time they are not expected, which detracts from the user experience. Still further, braking just before additional torque is required slows the trailing vehicle at a time when the lead vehicle is increasing its torque request which increases the risk that the gap will grow bigger than desired and can even lead to the front truck running away from the trailing truck if the trailing truck is unable to recover quickly enough.

The gap controller (gap regulator) architecture illustrated in FIG. 1 and described below helps mitigate these types of occurrences. In the illustrated embodiment, the gap regulator includes separate controllers (e.g. torque request controller 221 and brake request generator components 223) which are configured to control towards different gap control targets. The different control targets are illustrated in the state space diagrams of FIGS. 5A and 5B which show a control scheme in accordance with one specific implementation. More specifically, FIGS. 5A and 5B plot relative velocity between the vehicles (the Y-axis) vs. gap between the vehicles (the X-axis). FIGS. 5A and 5B also show a torque request controller target control line 320 and brake request controller target control line 330. FIG. 5A additionally shows representative transition paths from various points in the state space to the torque request target control line 320. Those transition lines are eliminated from FIG. 5B for clarity. In the illustrated embodiment, the nominal desired gap is 12 meters—which is represented by line 310. Thus, the target control point 311 is 12 meters with zero relative velocity, which is the point represented by the intersection of line 310 (12 meters gap) and line 312 (zero relative velocity).

The torque request controller component 221 of gap regulator 210 is configured to generate a torque request that is appropriate to control the gap in accordance with target control line 320. The torque request is then implemented by engine torque controller 152. As can be seen in FIGS. 5A and 5B, when the gap is larger than the desired gap, the rear truck is controlled to travel slightly faster than the front truck is traveling such that the relative velocity of the rear truck has a small positive value. As the rear truck draws closer to the lead truck, its relative velocity is reduced in a smooth manner until the gap is reduced to the target control point 311, at which point the relative velocity would be zero if perfect control were attained. If the rear truck gets closer than the desired gap, it is slowed so that it has a negative relative velocity relative to the lead truck to reestablish the desired gap.

For most open highway driving conditions, modulating the torque request alone is sufficient to control the gap appropriately without requiring the use of the foundation brakes. This is in part because the torque request can be negative to a certain degree without needing to actuate the foundation brakes through the use of engine braking and/or the retarder (if available). As mentioned above, when fuel is cut-off there will be some pumping losses and some frictional losses in the powertrain, so some level of negative torque can be provided while using normal valve timing by simply reducing the fuel charge appropriately. When larger negative torque is needed, the engine torque controller 152 can create larger negative torques by actuating the retarder and/or by taking other appropriate measures. Separately, the brake request controller component 223 of gap regulator 210 is arranged to generate brake requests during normal operation that are generally arranged to maintain a different gap—specifically a smaller gap—than the torque request controller 221 targets. This difference in the gaps that the torque and brake request controllers control to is sometimes referred to herein as the gap tolerance 340. In general, brake requests 213 are not generated unless or until the gap is reduced at least the gap tolerance below the torque request target control line 320.

In the embodiment illustrated in FIGS. 5A and 5B, the brake request controller 223 is configured to control the gap in accordance with brake target control line 330 under normal operating condition. It can be seen that target brake control line 330 is above and to the right of torque target control line 320. Thus, for example, in the illustrated embodiment, the nominal desired gap for the brake request controller 223 at zero relative velocity is 10 meters—which is two meters less than the target control point 311 for the torque request controller 221. That two meter difference is the gap tolerance 340 at a relative velocity of zero. The target brake control line 330 controls towards smaller gaps at other relative velocities as well. Since the brakes can only be used to slow the vehicle, the effect of this difference is that the trailing truck will be allowed to creep in a relatively small amount (2 meters in the example) before the foundation brakes are actuated when the gap regulator 210 cannot maintain the desired gap through control of the torque request alone. When the desired gap can be restored by modulating the torque requests alone without crossing target brake control line 330, then the foundation brakes do not need to be used at all. This has the effect of safely maintaining a gap while reducing the probability that the foundation brakes will be deployed unnecessarily.

It should be appreciated that the specific shape of the target control lines 320 and 330 may vary widely in accordance with the design goals for any particular controller. And there is no need for the lines to be parallel. Thus, the gap tolerance 340 (which may be viewed as the amount of “creep” or “squish” that is permitted) may vary as a function of the length of the current gap, the relative velocities of the vehicles and/or optionally, any other factors deemed appropriate to a particular application. In general, the amount of creep permitted before actuating the brakes may be higher when the distances between the platooning vehicles is further—although that is not a requirement.

The approach described above with reference to FIGS. 5A and 5B works well to help reduce the occurrences of the foundation brakes being used unnecessarily. However, there may be driving circumstances in which it will be desirable to actuate the foundation brakes immediately—even when the gap is currently greater than the targeted braking gap defined by control line 330. A good example of such a scenario is when the lead vehicle affirmatively brakes by actuating its foundation brakes. In such scenarios it may sometimes be desirable to try to avoid the creep permitted by the approach illustrated in FIGS. 5A and 5B. One way to address that issue is to change the brake control line when certain events are detected such as the lead vehicle braking.

The platoon controller 110 can be informed of the lead vehicle braking event by a message received from the lead vehicle (e.g., through a DSRC link) that the lead vehicle is braking or about to brake, by a camera or other sensor that detect the actuation of the lead vehicle's brake lights, or in any other suitable manner. In some circumstances in which the lead truck is being driven under human control, the braking message may be initiated by a controller on the lead vehicle when the driver first begins to depress the brake pedal, which may be a brief moment before the foundation brakes on the lead vehicle are deployed. This allows the control of the trailing vehicle to be very responsive.

When a lead vehicle braking event is detected, the brake request controller can be changed to utilize different control parameters. By way of example, one representative alternative is illustrated in FIG. 6. In this embodiment, the braking parameters are adjusted so that brake request control line 330′ coincides with a least a portion of the torque request control line 320. In the regions that coincides (which in the illustrated embodiments are regions corresponding to smaller gaps), the brake request controller 223 will seek to control to the same gap as the torque request controller 221. That is, the gap tolerance is changed to zero. This helps maintain the desired gap in times of affirmative lead vehicle braking which may provide a more desirable experience for passengers in the trailing vehicle.

Although setting the gap tolerance to zero as illustrated in FIG. 6 works well in many operational circumstances, there may be operational braking situations in which it is not desirable to snap to coinciding control of the torque and braking requests. Some such circumstances will be described with reference to two specific operational points 341 and 343 shown in FIG. 7. Point 341 represents a state in which the gap is larger than the nominal target gap 311 and the relative velocity between the lead and trailing vehicles is lower than the relative velocity desired for that particular gap size. In such a scenario the brake request controller can maintain relatively smooth braking when the brake request control snaps to the control line 330′ that coincides with the torque request control line.

Point 343 represents a state in which the gap is smaller than the nominal target gap 311 and the relative velocity between the vehicles is higher than desired for that particular gap size. In this state the gap controller is effectively using a portion of the allotted gap tolerance 340. This amount is sometimes referred to herein as the gap tolerance usage. It should be appreciated that the gap tolerance usage will vary with time as the gap controller seeks to control the trailing vehicle. In many circumstances the gap tolerance usage will be zero—as for example when the current state is somewhere along the torque request control line 320 or thereunder (e.g., as represented by point 341). In other transitory circumstances the gap usage may be lower than the permissible gap tolerance as represented by point 343. If the current operational state is a location along or above brake request control line 330, then the entire gap tolerance has been used.

Any time that a braking control target parameters switch occurs while the current operational state is at a position above the adjusted brake request control line 330′, as represented by point 343, there would be a sudden braking event or a sudden increase in the level of braking as the controller attempts to increase the gap while braking. That may be considered acceptable and/or desirable in many circumstances since braking is expected. In other circumstances, the impact of such a change in the control parameters may be considered “over-braking” since the braking controller will move to affirmatively grow the gap/reduce relative speed to the new brake request control line 330′. In alternative embodiments, to eliminate such over-braking in circumstances in which a portion of the gap tolerance is already in use when the active braking initiates, the brake request controller can set a new gap tolerance equal to the lower of the default tolerance and current usage of the gap tolerance. When the current usage is less than the default tolerance, this has the impact of causing the brake request controller to control the brakes to an intermediate brake control line 330″ which passes through the current state as best seen if FIG. 7.

In the illustrated embodiment the portions for the torque request control line 320 and the normal brake request control line 330 in a region within a few meters of the target gap 311 are parallel, with their separation corresponding to the gap tolerance. The active front vehicle braking brake request control line 330′ is coincident with the torque request control line in the same region. The current gap tolerance based brake request control line 330″ is also parallel with the torque request control line 320 in the same region, with the separation between 320 and 330″ corresponding to the gap tolerance usage at the time that the brake request controller's control parameters are changed. Although all of the illustrated control lines are parallel in this region in the illustrated embodiment—this is not a requirement in all embodiments. Rather, the control algorithms used in these different scenarios may vary in any manner deemed appropriate by the designer. As such there can be a variety of implementations in which the respective control lines are not parallel.

Although the example of changing the brake request controller's control line in response to lead vehicle braking events is given, it should be appreciated that the brake request controller can change its characteristics in response to any designated triggering event. For example, the control characteristics can be changed in response to actuation of a retarder on the lead vehicle, actuation the foundation brakes on the trailing vehicle regardless of what is happening with the lead vehicle or any other circumstance desired.

Additionally, in various embodiments, the desired gap and/or the gap tolerance can be varied based on driving conditions. For example, when driving in areas of rolling hills or in heavy traffic areas, it may be desirable to increase the gap and/or the gap tolerance.

Although only a few embodiments of the inventions have been described in detail, it should be appreciated that the inventions may be implemented in many other forms without departing from the spirit or scope of the invention. The inventions have been described primarily in the context of at least partially automatically controlling a trailing truck in a pair of platooning trucks. However, it should be appreciated that the same concepts can be applied to any types of vehicles operating in adaptive cruise control modes or in any type of connected vehicle applications, and regardless of whether the host vehicle is operating in a partially or fully automated operating mode.

Although a particular gap regulator architecture has been shown, it should be appreciated that the nature of the controllers used to perform the described gap control can vary widely. In some described embodiments, separate torque and brake request generators provided. However, in other embodiments a single controller or control algorithm can be arranged to generate both requests. In some of the described embodiments, a gap regulator generates the torque and braking requests and separate torque and brake controllers are utilized to implement those requests. However, in other embodiments, the gap regulator or other controller can be arranged to both (a) determine the amount of torque and/or braking required; and (b) control the delivery of the desired torque and/or braking.

As will be apparent to those familiar with the art, the described controllers can be implemented algorithmically using software or firmware algorithms executing on one or more processors, using programmable logic, using digital or analog components or using any combination of the preceding.

In vehicles that include retarders, the retarder can be controlled by a torque controller responsive to the torque request, or the brake controller responsive to the brake request or both. Alternatively, the retarder can be controlled directly by the gap regulator when the gap regulator also controls the delivery of the desired torque and/or braking.

In other embodiments appropriate for use in vehicles that utilize a retarder, gap regulator can be arranged to send a separate retard request to a retard controller or other the engine control component that controls the retarder. In such embodiments, the retarder can be controlled towards a retarder target control line that is different than the torque request and brake target control lines. If separate retarder control is provided, the retarder target control line would typically be intermediate between the torque request and brake request target control lines so as to encourage engine braking before retarding and retarding before the use of wheel brakes.

Some vehicles (particularly heavy vehicles) utilize multiple retarders. If desired, the retarders can be controlled separately in the described manner.

In the detailed description above, it is assumed that the controlled power plant is an internal combustion engine, as for example a diesel engine. However, it should be appreciated that the described control approach can be utilized regardless of the nature of the power plant used to provide torque to drive the host vehicle. Therefore, the present embodiments should be considered illustrative and not restrictive and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims. 

What is claimed is:
 1. A method of controlling a first vehicle to at least partially automatically maintain separation from a second vehicle while driving, the first vehicle having a power plant and brakes, the method comprising: automatically controlling an output of the power plant during driving in accordance with a power plant output control scheme arranged to attain and maintain a first target gap between the first and the second vehicles; and automatically controlling the brakes during driving in accordance with a braking control scheme arranged to attain and maintain a second target gap during first selected operating conditions, the second target gap being shorter than the first target gap.
 2. A method as recited in claim 1 wherein: the difference between the first and second target gaps is a gap tolerance; and the gap tolerance varies at least in part based on a current actual gap between the first and second vehicles.
 3. A method as recited in claim 1 wherein the power plant is an engine and the controlled brakes are wheel brakes.
 4. A method as recited in claim 1 wherein the first and second target gaps are longitudinal separations between the first and second vehicles.
 5. A method as recited in claim 1 wherein: the first vehicle is a truck that includes a retarder and wheel brakes; the retarder is controlled in accordance with the power plant output control scheme; and the wheel brakes are controlled in accordance with the braking control scheme.
 6. A method as recited in claim 2 wherein: the first vehicle is a truck that includes a retarder; the retarder is controlled in accordance with the power plant output control scheme when an actual gap between the first and second vehicles is greater than the second target gap; and the retarder is controlled in accordance with the braking control scheme when the actual gap between the first and second vehicles is less than the second target gap.
 7. A platoon controller for at least partially automatically controlling a host vehicle to attain and maintain a first target gap separation between the host vehicle and a second vehicle while the host vehicle is driving, the platoon controller comprising: a torque request controller configured to determine torque requests suitable for attaining and maintaining the first target gap between the host and second vehicles while the host vehicle is driving under first selected operating conditions; a brake request controller configured to determine brake requests suitable for attaining and maintaining a second target gap between the host and second vehicles while the host vehicle is driving under the first selected operating conditions, the second target gap being shorter than the first target gap; and wherein during driving under the first selected operation condition, the torque request controller outputs torque requests based on the first target gap and the brake request controller outputs brake requests based on the second target gap.
 8. A platoon controller as recited in claim 7 wherein: the difference between the first and second target gaps is a gap tolerance; and the gap tolerance varies at least in part based on a current actual gap between the host and second vehicles.
 9. A platoon controller as recited in claim 8 wherein: the host vehicle is a truck that includes a retarder; the retarder is controlled in accordance with the power plant output control scheme when an actual gap between the first and second vehicles is greater than the second target gap; and the retarder is controlled in accordance with the braking control scheme when the actual gap between the first and second vehicles is less than the second target gap.
 10. A platoon controller as recited in claim 7 wherein: the host vehicle is a truck that includes a retarder and wheel brakes; the retarder is controlled in accordance with the power plant output control scheme; and the wheel brakes are controlled in accordance with the braking control scheme. 